Systems and methods for initiating electronic remediation actions

ABSTRACT

Embodiments of the present disclosure are directed to a system, methods, and computer-readable media for automatically initiating post-delivery action based on pre-tender diagnostic test results and post-delivery diagnostic test results stored in a distributed electronic ledger for a particular item. In embodiments, the post-delivery action can include, among other things, automatically initiating a return action such as generating shipment information for a return of the item, initiating an insurance action for the item, and/or communicating an electronic notification to the item seller and/or item purchaser. The post-delivery action can be stored in the distributed electronic ledger, and the post-delivery action can electronically trigger a cascade of returns, billing, communications, and/or insurance actions, among other things.

BACKGROUND

Generally, an entity may sell electronic goods or services to consumers.After control of the electronic goods or services is passed to theconsumer, for example by physical or virtual delivery of the electronicgoods or services, the electronic goods or services may malfunction. Anentity is generally unable to determine any such malfunction, and anyextent of the malfunction at that time, as the electronic goods orservices reside with the consumer. Additionally, the entity is generallyunable to surmise whether consumer-inflicted misuse resulted in themalfunction, as opposed to rough package handling, for example.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The present invention is defined by the claims as supported bythe Specification, including the Detailed Description and Drawings.

In brief and at a high level, various embodiments of the presentinvention provide systems, methods, and computer-readable media thatleverage the immutability of the distributed electronic ledger toautomatically initiate electronic actions based on pre-tender diagnostictest results and post-delivery diagnostic test results for an end-usercomputing device, wherein the pre-tender and post-delivery diagnosistest results are automatically determined and stored in a distributedelectronic ledger.

In some embodiments, one or more non-transitory computer-readable mediahaving computer instructions stored thereon for execution by one or moreprocessors is provided, wherein execution of the computer instructionsvia the one or more processors results in a method. The method caninclude receiving shipment creation information for an item from anentity server, wherein the shipment creation information includes anitem identifier for the item and pre-tender diagnostic information forthe item. The method can further include generating a transactionincluding the shipment creation information based on the receiptthereof. The generated transaction can be communicated to a network,wherein a plurality of nodes of the network is configured to store thecommunicated transaction to a distributed ledger. The method can furtherinclude monitoring the distributed ledger, via the network, to detectwhen a subsequent transaction corresponding to the item identifier isstored in the distributed ledger, wherein the subsequent transactionincludes post-delivery diagnostic information for the item. The methodcontinues, for example, by receiving a notification from the entityserver, indicating a determination that the post-delivery diagnosticinformation for the item is different than the pre-tender diagnosticinformation for the item. An electronic remediation action can then begenerated based on the determination that the post-delivery diagnosticinformation included in the detected subsequent transaction is differentthan the pre-tender diagnostic information included in the storedtransaction.

In some other embodiments, one or more non-transitory computer-readablemedia having computer instructions stored thereon for execution by oneor more processors is provided, wherein execution of the computerinstructions via the one or more processors results in a method. Themethod can include receiving shipment creation information for an itemfrom an entity server, wherein the shipment creation informationincludes an item identifier for the item and pre-tender diagnosticinformation for the item. A transaction is generated that includes theshipment creation information based on the receipt thereof. Thegenerated transaction can be communicated to a network, wherein aplurality of nodes of the network is configured to store thecommunicated transaction to a distributed ledger. The distributed ledgercan be monitored, via the network, to detect when a subsequenttransaction corresponding to the item identifier is stored in thedistributed ledger, the subsequent transaction including post-deliverydiagnostic information for the item. A notification from the entityserver can be received, indicating a determination that thepost-delivery diagnostic information for the item matches the pre-tenderdiagnostic information for the item. A determination can be made that anelectronic remediation action is not to be generated based on thenotification received indicating the determination that thepost-delivery diagnostic information for the item matches the pre-tenderdiagnostic information for the item.

In some other embodiments, a system is provided. The system includes aserver associated with a carrier entity. The server includes acommunication component. The communication component can be configuredfor receiving shipment creation information for an item from an entityserver, wherein the shipment creation information includes an itemidentifier for the item and pre-tender diagnostic information for theitem. In some embodiments, the communication component is furtherconfigured for communicating a generated transaction to a network,wherein a plurality of nodes of the network is configured to store thecommunicated transaction to a distributed ledger. The communicationcomponent can be configured for receiving a notification from the entityserver, indicating a determination that the post-delivery diagnosticinformation for the item is different than the pre-tender diagnosticinformation for the item. The system, in some embodiments, can include atransaction component configured for generating the transactionincluding the shipment creation information based on the receiptthereof. The server, in some embodiments, can include a surveillancecomponent. The surveillance component is configured for monitoring thedistributed ledger, via the network, to detect when a subsequenttransaction corresponding to the item identifier is stored in thedistributed ledger, wherein the subsequent transaction includespost-delivery diagnostic information for the item. The server canfurther include a remediation component configured for automaticallygenerating an electronic remediation action based on the determinationthat the post-delivery diagnostic information included in the detectedsubsequent transaction is different than the pre-tender diagnosticinformation included in the stored transaction.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawings figures, wherein:

FIG. 1 illustrates a computing environment in accordance with anembodiment of the present invention;

FIG. 2 illustrates a carrier server in accordance with an embodiment ofthe present invention;

FIG. 3 illustrates a non-carrier server in accordance with an embodimentof the present invention;

FIG. 4 illustrates a diagram of component interactions in accordancewith an embodiment of the present invention;

FIG. 5 illustrates a method in accordance with an embodiment of thepresent invention;

FIG. 6 illustrates another method in accordance with an embodiment ofthe present invention; and

FIG. 7 illustrates a computing device in accordance with an embodimentof the present disclosure.

DETAILED DESCRIPTION OF THE INVENTION

The subject matter of the present invention is being described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step,” “instance,” and/or “block” can be used hereinto connote different elements of methods employed, the terms should notbe interpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described. The present disclosure will now bedescribed more fully herein with reference to the accompanying drawings,which may not be drawn to scale and which are not to be construed aslimiting. Indeed, the present invention can be embodied in manydifferent forms and should not be construed as limited to theembodiments set forth herein.

FIG. 1 illustrates a computing environment 100 that is suitable forimplementation of the present invention. The computing environment 100of FIG. 1 comprises one or more servers. The one or more servers cancommunicate, directly or indirectly, with one another via a network 102.In one embodiment, the network 102 is a distributed network. As usedherein, a distributed network is a network comprising one or morecomputing devices or nodes that are not located together, for example,such that the nodes of the network are remote from one another. It willbe understood that a distributed network can be implemented forfacilitating or enabling (e.g., receiving, processing, sending) any andall interactions discussed herein. The network 102 can include wirelessand/or physical (e.g., hardwired) connections. Non-limiting examples ofnetworks include a telecommunications network, Wide Area Network (WAN),a Local Area Network (LAN), a Wireless Local Area Network (WLAN), aWi-Fi network, a short range wireless network, a Wireless MetropolitanArea Network (WMAN), a Bluetooth® capable network, a fiber opticnetwork, or a combination thereof. The network 102 provides the one ormore servers access to the Internet and web-based applications, invarious embodiments.

In embodiments, one or more of the servers in the computing environment100 is associated with components, those components being associatedwith a carrier entity, a non-carrier entity, an end-user entity, or acombination thereof. As shown in FIG. 1 , the computing environment 100comprises a carrier server 104, which is a server associated with acarrier entity. A carrier entity can be an entity that facilitates theorganization and transportation of packages, parcels, and/or freight forshipment and delivery, in embodiments. In some embodiments, a carrierentity can further comprise an entity responsible for “last-miledelivery” or shipment fulfillment. It will be understood that the terms“carrier entity” and “carrier server” are not to be construed aslimiting. For example, an entity and associated server can correspond toany company, retailer, wholesaler, and/or manufacturer, in someembodiments. Accordingly, the term “carrier” is used herein as anidentifier so that a particular entity and associated server can bediscussed and distinguished from other entities. As described herein,the carrier server 104 can comprise one or more of a communicationcomponent 106, a transaction component 108, a surveillance component110, or a remediation component 111, as shown in FIG. 2 . The computingenvironment 100 further comprises a non-carrier server 112, which is aserver associated with a non-carrier entity. A non-carrier entity can bean entity that sells goods or services virtually, through an Internetconnection, through an application (e.g., software), and/or through abrick-and-mortar storefront. A non-carrier entity can be an entity sucha merchant entity, a retail entity, a wholesale entity, a refurbishingentity, a repair entity, and/or a secondary market entity (e.g., sellingof a used item or a returned item). It will be understood that the terms“non-carrier entity” and “non-carrier server” are not to be construed aslimiting. For example, an entity and associated server can correspond toany company, retailer, wholesaler, and/or manufacturer, in embodiments.Accordingly, the term “non-carrier” is used herein as an identifier sothat a particular entity and associated server can be discussed anddistinguished from other entities. In embodiments, the non-carrierserver 112 can comprise, described herein, one or more of a diagnosticassessment component 114 or a notification component 116, as shown inFIG. 3 . The computing environment 100 further comprises an end-usercomputing device 118, which is an electronic device that comprises aprocessor and memory, in embodiments. The terms “end-user computingdevice” and “item” are used interchangeably herein.

In embodiments, the carrier server 104, non-carrier server 112, theend-user computing device 118, or a combination thereof, canbi-directionally communicate with one another, whether the electroniccommunications are sent via direct links or indirect links. Additionallyor alternatively, the carrier server 104, non-carrier server 112, theend-user computing device 118, or a combination thereof, canelectronically communicate with one another using the network 102.Further, the carrier server 104, non-carrier server 112, the end-usercomputing device 118, or a combination thereof, can electronicallycommunicate directly with one or more nodes 120 and/or directly with thedistributed electronic ledger 122, which are connected to the network102. In embodiments, each of the one or more nodes 120 is a remotecomputing device. Each of the one or more nodes 120 can manage theverification of transactions, the generation of transactions, and thestorage of transactions to a distributed electronic ledger 122, inembodiments. However, it will be understood from the discussionhereinafter that because each of the carrier server 104, non-carrierserver 112, the end-user computing device 118 can communicate directlywith the distributed electronic ledger, each of the carrier server 104,non-carrier server 112, the end-user computing device 118 can manage theverification of transactions, the generation of transactions, and thestorage of transactions to a distributed electronic ledger 122, in someembodiments. In accordance with embodiments described herein. A“transaction” can be defined as an electronic data object or otherelectronic data structure that is defined, stored, and/or generated by acomputing device. In operation, the computing environment 100facilitates interactions, whether direct or indirect, between thecarrier server 104, non-carrier server 112, the end-user computingdevice 118, the one or more nodes 120, or a combination thereof.

At a high level, the components of the computing environment 100leverage the immutability of the distributed electronic ledger 122 inorder to, for example, automatically initiate electronic actions basedon pre-tender diagnostic test results and post-delivery diagnostic testresults for the end-user computing device 118 (i.e., “item”), thepre-tender and post-delivery diagnosis test results being stored in adistributed electronic ledger 122. An electronic action can comprise thenon-carrier server 112 using the pre-tender diagnostic test results forthe end-user computing device 118 and the post-delivery diagnostic testresults for the end-user computing device 118 to determine whether theend-user computing device 118 is operational, is non-operational, and/oris operating within predetermined diagnostic thresholds and/or baselines(e.g. “normal” operations), in various embodiments. The diagnostic testresults can quantify the functionality of the hardware and softwareoperations of a system of the end-user computing device 118, in anembodiment. Additionally, in one example, the electronic action cancomprise the non-carrier server 112 generating and communicating anotification, directly or indirectly, to the carrier server 104,regarding one or more determinations. The notification can include,additionally or alternatively, data encoding contact information and/ora unique identifier for an end-user associated with the end-usercomputing device, the end-user computing device 118 itself, and/or arequest for carrier-provided services to be implemented regarding theend-user computing device 118. In a further example, the carrier server104 can initiate an electronic action based on, or in response to, thenotification received from the non-carrier server 112 regarding one ormore determinations for the end-user computing device 118 and theoperations of the end-user computing device 118. The carrier server 104can initiate an electronic action such as an electronic remediationaction. Non-limiting examples of electronic remediation actions caninclude generating electronic shipment information, generating ashipping label, requesting or authorizing a return authorization request(RMA), or a combination thereof. Further, the carrier server 104 cancommunicate the shipment information and/or a generated the shippinglabel to the non-carrier server 112, the end-user computing device 118,and/or another computing device associated with the end user (notshown). For example, a generated shipping label can be communicated toan alternative computing device associated with the end user orelectronic account associated for the end user, so that the shippinglabel can be accessed by the end-user via the alternative computingdevice and/or account in the scenario where the end-user computingdevice 118 is determined to be non-operational. Non-limiting examples ofelectronic remediation actions can also include generating electronicnotifications comprising warranty information, product registrationinformation, and/or insurance information associated with the end-usercomputing device 118. For example, the carrier server 104 cancommunicate warranty and/or insurance information to the non-carrierserver 112, the end-user computing device 118, and/or another computingdevice associated with a third party (not shown).

As discussed above, the components of the computing environment 100leverage a distributed electronic ledger 122 in order to automaticallyinitiate electronic actions based on pre-tender diagnostic test resultsand post-delivery diagnostic test results for the end-user computingdevice 118. Discussed herein is a detailed description of the componentsof the computing environment 100, and their interactions with oneanother, including the one or more nodes 120 that perform theverification, generation, and storage of transactions to the distributedelectronic ledger 122. Turning to FIG. 4 , a diagram 400 of saidcomponent interactions is illustrated in accordance with an embodimentof the present invention.

Generally, a non-carrier entity, such as a seller entity, a merchantentity, a retail entity, a wholesale entity, a refurbishing entity, arepair entity, or a secondary market entity (e.g., selling of a useditem or a returned item), has physical possession or control of theend-user computing device 118 (i.e., “item”). Prior to packaging andshipping the end-user computing device 118 to a location associated withan end user, a diagnostic tool can be used to determine whether theend-user computing device 118 is operational or non-operational. Thediagnostic tool can be software or an application user interface (API)that is installed on the end-user computing device 118, and/or can beaccessible at the end-user computing device 118 and/or through a networkconnection (e.g., the Internet). When the diagnostic tool is initiated,one or more diagnostic tests are performed, via one or more processorsof the end-user computing device 118, shown at instance 402 in FIG. 4 .In some aspects, the diagnostic tool can be initiated upon powering onthe end-user computing device 118, whether for a predetermined number oftimes or an indeterminate number of times. In some further aspects, thediagnostic tool can be initiated upon a first boot (e.g., upon aninitial starting or powering on just prior to packaging and/or shipping)and a second boot (e.g., upon an initial starting or powering on justafter delivery), as will be described. Output (e.g., data encodingmeasurements) of the one or more diagnostic tests is recorded, regardingthe functions and operations of software, hardware, or a combinationthereof, of the end-user computing device 118. The output of thediagnostic tool can be communicated from the end-user computing device118 to the non-carrier server 112 as shown in instance 404 of FIG. 4 .However, in some embodiments, the output of the diagnostic tool can becommunicated directly to the one or more nodes 120 or directly to thedistributed electronic ledger 122.

In one embodiment, the end-user computing device 118 automaticallyinitiates the diagnostic assessment in response to being powered “on,”for example. In some embodiments, the non-carrier server 112 or thediagnostic assessment component 114 thereof initiates the diagnosticassessment for reporting on system performance of an item prior totender of the item to a carrier entity for shipment. In someembodiments, the diagnostic assessment component 114 of the non-carrierserver 112 can electronically communicate computer-readable instructionsor a request to the end-user computing device 118, wherein the end-usercomputing device 118 executes the computer-readable instructions via oneor more processors in order to perform one or more diagnostic tests andgenerate output from the one or more diagnostic tests. Generally, theoutput of the one or more diagnostic tests that are performed at theend-user computing device 118 prior to tender of the end-user computingdevice 118 to a carrier entity, can be an output that comprisespre-tender diagnostic information that is specific to the end-usercomputing device 118. Generally, pre-tender diagnostic informationindicates diagnostic test results that report on system performance ofthe item as measured prior to tender of the item to a carrier entity.The pre-tender diagnostic information can be communicated directly tothe one or more nodes 120 or directly distributed electronic ledger 122,in some embodiments. In another embodiment, the pre-tender diagnosticinformation can be communicated to one or more of the non-carrier server112 or carrier server 104.

When the output of the diagnostic tool is communicated from the end-usercomputing device 118 to the non-carrier server 112, the diagnosticassessment component 114 can use the pre-tender diagnostic informationlocated on the distributed electronic ledger 122 to determine whetherthe end-user computing device 118 is operational, is non-operational,and/or is operating within predetermined diagnostic thresholds and/orbaselines (e.g. “normal” operations), as shown at instance 406 of FIG. 4. The pre-tender diagnostic information can quantify the functionalityof the hardware and software operations of a system of the end-usercomputing device 118, in an embodiment. In some embodiments, thediagnostic assessment component 114 obtains raw data as output from theone or more diagnostic tests performed. In such an embodiment, thediagnostic assessment component 114 can receive raw data and generatepre-tender diagnostic information regarding the software and hardwareoperations and system performance of the item.

Additionally, the non-carrier server 112 or the diagnostic assessmentcomponent 114 thereof can associate the pre-tender diagnosticinformation of the output with a unique identifier, the uniqueidentifier being associated with the end-user computing device 118, insome embodiments. In one embodiment, the non-carrier server 112 or thediagnostic assessment component 114 thereof can electronically associateor link a serial number of the end-user computing device 118 with thepre-tender diagnostic information. Additionally or alternatively, thenon-carrier server 112 or the diagnostic assessment component 114thereof can electronically associate or link an item identifier of theof the end-user computing device 118, a model number of the end-usercomputing device 118, a manufacturing date of the end-user computingdevice 118, a manufacturing batch number of the end-user computingdevice 118, a manufacturing location of the end-user computing device118, a serial number of the end-user computing device 118, a serialnumber of one or more subcomponents of the end-user computing device118, or a combination thereof, with the pre-tender diagnosticinformation. In an embodiment, the non-carrier server 112 can store theinformation and the links or associations between said information inlocal and/or remote memory. The non-carrier server 112 can communicatethe information and the links or associations between said informationto the carrier server 104, in an embodiment. As such, the non-carrierserver 112 and/or the carrier server 104 can communicate the informationand the links or associations between said information to the one ormore nodes 120, via the network 102.

In embodiments, the notification component 116 of the non-carrier server112 can send communications. In an embodiment, the non-carrier server112 or the notification component 116 thereof electronicallycommunicates information to the carrier server 104 regarding theend-user computing device 118, as shown at instance 408A of FIG. 4 .Alternatively, in an embodiment, the non-carrier server 112 or thenotification component 116 thereof electronically communicatesinformation regarding the end-user computing device 118 directly to oneor more nodes 120 or the distributed electronic ledger 122, thusbypassing the carrier server 104 as shown at instance 408B of FIG. 4 .The information can comprise shipment creation information for theend-user computing device 118. Non-limiting examples of shipmentcreation information can include an item identifier for the end-usercomputing device 118, pre-tender diagnostic information for the end-usercomputing device 118, contact information for an end-user associatedwith the end-user computing device 118, geographic location associatedwith a destination (e.g., a physical mailing address whether residentialor commercial, such as a carrier retail location and/or any intermediaryshipping warehouses) for the end-user computing device 118, and thelike, in various embodiments. Non-limiting examples of shipment creationinformation can include a service level for the end-user computingdevice 118, a service level for the non-carrier entity associated withthe non-carrier server 112, handling instructions for the end-usercomputing device 118, handling instructions for the non-carrier entityassociated with the non-carrier server 112, a service level associatedwith regulatory compliance for the end-user computing device 118,handling instructions associated with regulatory compliance for theend-user computing device 118, or a combination(s) thereof. The shipmentcreation information can include a request for a carrier entityassociated with the carrier server 104 to create a shipping record forthe end-user computing device 118, for example, in anticipation of, orin response to, tender of the end-user computing device 118 to thecarrier entity for shipment, in embodiments. A request for performanceof carrier entity services for the end-user computing device 118 can begenerated by the non-carrier server 112 or the notification component116 thereof, and included with the shipment creation information.

Accordingly, at instance 408, the carrier server 104 can receive theinformation, such as shipment creation information, from the non-carrierserver 112 or from the distributed electronic ledger 122. In furtherembodiments, the communication component 106 of the carrier server 104can receive the shipment creation information for the end-user computingdevice 118 from the non-carrier server 112, wherein the shipmentcreation information includes an item identifier for the of the end-usercomputing device 118 and pre-tender diagnostic information for the ofthe end-user computing device 118. The shipment creation information cancomprise one or more of an item identifier, pre-tender diagnosticinformation, or a request for creation of a shipping record for the ofthe end-user computing device 118. The transaction component 108 of thecarrier server 104 can generate a transaction including the shipmentcreation information based on the receipt thereof, as shown at instance410 of FIG. 4 . The transaction can comprise the shipment creationinformation, including pre-tender diagnostic information for theend-user computing device 118. The carrier server 104 or thecommunication component 106 thereof can communicate the generatedtransaction, via the network 102, to one or more nodes 120, as shown atinstance 412.

Generally, the one or more nodes 120 comprise a plurality of nodes thatcommunicate via the network 102. In embodiments, the plurality of nodesverify transactions with one another, and only verified transactions arestored to the distributed electronic ledger 122. In some embodiments,the carrier server 104 and/or the non-carrier server 112 can function asnodes that facilitate verification of transactions. The one or morenodes 120 are configured to perform a verification of the transaction,as shown at instance 414 of FIG. 4 . After an affirmative verification,the transaction can be further communicated to the distributedelectronic ledger 122, as shown at instance 416. Then, the communicatedtransaction can be stored to the distributed electronic ledger 122, asshown at instance 418. The distributed electronic ledger comprises data,the data being indicative of transactions. Transactions and data forthose transactions can be represented as a plurality of “blocks.” One ormore transactions that are communicated to the plurality of nodes areused to generate a new block once the transactions are verified by amajority of the plurality of nodes, generally. Each new block can beelectronically added and linked to prior-in-time blocks in thedistributed electronic ledger 122, thus providing a sequential andlinked “blockchain” indicative of the transactions for which data can bestored in the distributed electronic ledger 122. Moreover, each blockcan represent and/or comprise data identifying one or more particulartransactions, pre-tender diagnostic information, shipping creationinformation, item identifiers, non-carrier entity information, end userinformation, contact information for an end user, carrier servicesbehavior (e.g., type, volume, service level used by entity when actingas a customer of a carrier), item characteristics, delivery information,location identifiers, and/or addresses that are each indicative of anon-carrier entity, a recipient or end user of an item, a carrierentity, and/or location having prior, present, or future control overthe end-user computing device 118, in embodiments. In variousembodiments, a new block can be generated and added to a blockchain ofthe distributed electronic ledger 122 upon receipt of information and/ordata indicating one or more of: a subsequent transaction, tender of anitem to a carrier, static and/or dynamic location information of an item(e.g., progressive parcel tracking using identifier scanning and nearreal-time location tracking of a parcel through carrier distributionchannels and/or via delivery vehicles), delivery of an item to alocation, delivery confirmation, or a change in control of the end-usercomputing device 118 between one or more entities. It is furthercontemplated that each block can be associated with and/or include atimestamp that can be generated by one or more of the nodes 120 uponreceiving the transaction.

In embodiments, the carrier server 104 or the surveillance component 110thereof monitors the distributed electronic ledger 122, via the network102. Although not shown in FIG. 4 , the surveillance component 110 cancommunicate one or more requests to the nodes 120 for informationregarding additional and/or subsequent transactions and/or blocks thathave been added to the distributed electronic ledger 122. These requestscan be communicated periodically, in some embodiments. As such, in someembodiments, one or more nodes 120 monitor the distributed electronicledger 122 and provide a notification to the carrier server 104 ofsubsequent transactions added to the distributed electronic ledger 122,such that the carrier server 104 can indirectly monitor the distributedelectronic ledger 122 by monitoring the one or more nodes 120. Thecarrier server 104 or the surveillance component 110 thereof cantherefore detect when a subsequent transaction is added to thedistributed electronic ledger 122, based on the monitoring. In furtherembodiments, the carrier server 104 or the surveillance component 110thereof can detect when a subsequent transaction that corresponds to theitem identifier is stored to the distributed electronic ledger 122,based on the monitoring.

In some embodiments, the surveillance component 110 can identify, viathe network 102 and/or the one or more nodes 120, a subsequenttransaction that corresponds to the item identifier. In a furtherembodiment, the surveillance component 110 can identify the previouslystored transaction (i.e., having the pre-tender diagnostic information)on the distributed ledger, based on the detection of the subsequenttransaction corresponding to the item identifier. The subsequenttransaction can comprise one or more of an item identifier orpost-delivery diagnostic information for the end-user computing device118, in various embodiments. Generally, post-delivery diagnosticinformation indicates diagnostic test results that report on systemperformance of the end-user computing device 118, as measured subsequentto delivery of the end-user computing device 118 by the carrier toanother controlling entity, such as an end user.

The post-delivery diagnostic information indicates diagnostic testresults that report on system performance as measured at any timesubsequent to delivery of the end-user computing device 118 by thecarrier to another controlling entity, such as an end user. Accordingly,in some embodiments, the post-delivery diagnostic information canindicate system performance as measured by a diagnostic test performedwithin one day of delivery, within one week of delivery, within one yearof delivery, within a predefined period of time that corresponds to aparts or manufacturing warranty, and/or within a predefined period oftime that corresponds to a return policy, for example. Additionally oralternatively, post-delivery diagnostic information can indicate systemperformance as measured by a diagnostic test performed periodically, forexample, once a week, twice per week, bi-monthly, monthly, quarterly,semi-annually, annually, and/or another predefined period of time.Therefore, post-delivery diagnostic information can be communicated as atransaction to be added to the distributed electronic ledger 122 eachtime that post-delivery information is obtained, e.g., once, more thanonce, or on a reoccurring basis, whether system performance testing ismanual or automatic. Further, the non-carrier server 112, the carrierserver 104, and/or the surveillance component 110 can monitor thedistributed electronic ledger 122 in order to recognize when postdiagnostic test results are added to the distributed electronic ledger122 as one or more transactions, whether added once, more than once,intermittently, and/or periodically, and spanning any amount of timeafter delivery.

In some embodiments, when the surveillance component 110 detects that asubsequent transaction corresponding to the item identifier is added tothe distributed electronic ledger 122, the carrier server 104 canmonitor the non-carrier server 112 in anticipation of receipt of anotification from the non-carrier server 112. The carrier server 104 canmonitor the non-carrier server 112 in anticipation of receipt of suchnotification for a predefined period of time, wherein upon lapse orexpiration of the predefined period of time, the carrier server 104terminates monitoring the non-carrier server 112, in an embodiment. Thesurveillance component 110 can continue to monitor the distributedelectronic ledger 122 while the carrier server 104 simultaneouslymonitors the non-carrier server 112, in one embodiment.

Additionally or alternatively, the non-carrier server 112 can monitorthe distributed electronic ledger 122, via the network 102. Thenon-carrier server 112 can detect when a subsequent transaction is addedto the distributed electronic ledger 122, in some embodiments. Infurther embodiments, the non-carrier server 112 can detect when asubsequent transaction that corresponds to the item identifier is storedto the distributed electronic ledger 122. The subsequent transaction cancomprise a delivery information and/or a notification of delivery forthe end-user computing device 118, in one embodiment.

Continuing with FIG. 4 , post-delivery diagnostic information for theend-user computing device 118 can be stored to the distributedelectronic ledger 122 in a “block” that comprises one or moretransactions, in some embodiments. For example, subsequent to delivery,the end-user computing device 118 can be powered “on.” In oneembodiment, in response to being powered “on,” the diagnostic tooloperating at the end-user computing device 118 can be initiated, and oneor more diagnostic tests can be performed, via one or more processors ofthe end-user computing device 118, as shown at instance 420.Alternatively, the diagnostic tool can be initiated in response to userinput, via the end-user computing device 118, wherein the user inputindicates performance of the one or more diagnostic tests is desired.Output of the one or more diagnostic tests can be recorded, regardingthe functions and operations of software, hardware, or a combinationthereof, of the end-user computing device 118 subsequent to delivery tothe end user, in embodiments. This output can comprise post-deliverydiagnostic information of the end-user computing device 118. Generally,the output of the one or more diagnostic tests that are performed at theend-user computing device 118 subsequent to delivery of the end-usercomputing device 118 from a carrier entity to an end user, can be anoutput that comprises post-delivery diagnostic information that isspecific to the end-user computing device 118. In embodiments, theoutput of the diagnostic tool can be communicated from the end-usercomputing device 118 to the non-carrier server 112, as shown in instance422. Additionally or alternatively, the output can be communicated tothe one or more nodes 120 as a new transaction, for verification andstorage to the distributed electronic ledger 122. The output cancomprise a unique item identifier, as previously discussed regarding thepre-tender diagnostic information. In embodiments, the diagnostics testsare performed at the first instance of the end-user computing device 118being powered up after delivery. As such, the operation of the end-usercomputing device 118 is assessed at the initial post-delivery power-up,prior to any subsequent end-user handling, use, misuse, softwareinstallations, and/or tampering of the end-user computing device 118.However, in some embodiments, the operation of the end-user computingdevice 118 is assessed by diagnostic testing one or more times after theinitial post-delivery power-up, and/or after end-user handling hasoccurred, as mentioned above.

In one embodiment, the diagnostic assessment component 114 of thenon-carrier server 112 receives output from the one or more diagnostictests performed subsequent to delivery, as communicated from theend-user computing device 118. The output can comprise the post-deliverydiagnosis information, and the output and/or the post-deliverydiagnostic information can be associated with the item identifier, insome embodiments. As such, the non-carrier server 112 can use the itemidentifier to perform operations as further discussed herein.

In one embodiment, the diagnostic assessment component 114 receives rawdata as output from the one or more diagnostic tests performedsubsequent to delivery, as communicated from the end-user computingdevice 118. In such an embodiment, the diagnostic assessment component114 can generate post-delivery diagnostic information regarding thesoftware and hardware operations and system performance of the end-usercomputing device 118, using the raw data and the item identifier. Thenon-carrier server 112 or the diagnostic assessment component 114thereof can also retrieve the pre-tender diagnostic information from thedistributed electronic ledger 122, via the network 102, in oneembodiment. The item identifier can be used to locate and/or retrievethe pre-tender diagnostic information. For example, the storedtransaction including the shipment creation information on thedistributed electronic ledger 122 can be identified based on thedetection of the subsequent transaction, by the non-carrier server 112,by the carrier server 104, and/or by the one or more nodes 120, invarious embodiments. Additionally or alternatively, the non-carrierserver 112 or the diagnostic assessment component 114 thereof canretrieve the pre-tender diagnostic information from memory of thenon-carrier server 112, in one embodiment.

Accordingly, subsequent to receiving the output comprising thepost-delivery diagnostic information and the item identifier, thenon-carrier server 112 or the diagnostic assessment component 114thereof can use the pre-tender diagnostic information for the end-usercomputing device 118 and the post-delivery diagnostic information forthe end-user computing device 118 to determine whether the end-usercomputing device 118 is operational, non-operational, and/or operatingwithin predetermined diagnostic thresholds and/or baselines (e.g.“normal” operations) after delivery. The non-carrier server 112 or thediagnostic assessment component 114 thereof can determine whether thepost-delivery diagnostic information matches the pre-tender diagnosticinformation stored to the distributed electronic ledger 122. Thenon-carrier server 112 or the diagnostic assessment component 114thereof can determine that the post-delivery diagnostic information isan identical match to the pre-tender diagnostic information, in oneembodiment. In one such an embodiment, the non-carrier server 112 or thediagnostic assessment component 114 thereof can further determine thatthe non-identical post-delivery diagnostic information is equivalent toa match to the pre-tender diagnostic information when values of thepost-delivery diagnostic information are within a predetermined range ofvalues of the pre-tender diagnostic information. In yet anotherembodiment, the non-carrier server 112 or the diagnostic assessmentcomponent 114 thereof can determine that the non-identical post-deliverydiagnostic information is equivalent to a match to the pre-tenderdiagnostic information when values of the post-delivery diagnosticinformation meet or exceed one or more predefined thresholds fordiagnostic information.

When it is determined that the post-delivery diagnostic informationmatches the pre-tender diagnostic information, the notificationcomponent 116 of the non-carrier server 112 automatically generates anotification indicating that the post-delivery diagnostic informationmatches the pre-tender diagnostic information, shown at instance. Thenon-carrier server 112 can communicate the notification to the carrierserver 104. In one such embodiment, communication component 106 of thecarrier server 104 receives the notification from the non-carrier server112, the notification indicating the determination that thepost-delivery diagnostic information for the end-user computing device118 matches the pre-tender diagnostic information for the end-usercomputing device 118. Then, the carrier server 104 can determine that anelectronic remediation action is not to be generated based on thenotification received indicating the determination that thepost-delivery diagnostic information for the end-user computing device118 matches the pre-tender diagnostic information for the end-usercomputing device 118, in such an embodiment.

When it is determined that the post-delivery diagnostic information doesnot match the pre-tender diagnostic information, or is not equivalent toa match to the pre-tender diagnostic information, the notificationcomponent 116 of the non-carrier server 112 automatically generates anotification, shown at instance 424 of FIG. 4 . The notificationindicates the determination that the post-delivery diagnosticinformation does not match, or is not equivalent to, a match for thepre-tender diagnostic information, in an embodiment. In someembodiments, the notification comprises the item identifier. Thenotification can comprise contact information, in some embodiments.Non-limiting examples of contact information can include a physicalmailing address of an end user that is associated with the end-usercomputing device 118, a telephone number of an end user that isassociated with the end-user computing device 118, an email address ofan end user that is associated with the end-user computing device 118,or any identifier for the end user, for a computing device associatedwith the end user, and/or for a physical delivery destination associatedwith the end-user computing device 118 and/or the end user. Thenotification can be communicated from the non-carrier server 112 to thecarrier server 104, as shown at instance 426 of FIG. 4 .

In embodiments, the communication component 106 of the carrier server104 is configured to receive the notification from the non-carrierserver 112, wherein the notification indicates the determination thatthe post-delivery diagnostic information for the end-user computingdevice 118 is different than the pre-tender diagnostic information forthe end-user computing device 118. In some embodiments, the notificationcan comprise the item identifier associated with the end-user computingdevice 118 for which the post-delivery diagnostic information does notmatch the pre-tender diagnostic information. Additionally oralternatively, the notification can comprise contact information, asdescribed above.

Based on the notification, the remediation component 111 of the carrierserver 104 can generate an electronic remediation action, as shown atinstance 428 of FIG. 4 . In an embodiment, the generation of theelectronic remediation action can be based on the determination that thepost-delivery diagnostic information, as included in the detectedsubsequent transaction, is different than the pre-tender diagnosticinformation included in the stored transaction. In one embodiment, theelectronic remediation action is automatically generated based furtheron another determination that the post-delivery diagnostic informationcorresponds to one or more predefined diagnostic baseline criteria. Inone embodiment, the electronic remediation action can be automaticallygenerated by the remediation component 111 based on the determinationthat the post-delivery diagnostic information included in the detectedsubsequent transaction is different than the pre-tender diagnosticinformation included in the stored transaction, or based on thedetermination that the post-delivery diagnostic information correspondsto one or more predefined diagnostic baseline criteria.

In another example, the non-carrier server 112 and/or the carrier server104 can communicate 427A and 427B with the distributed electronic ledger122 for initiating the generation of electronic remediation action. Inon such an example, the electronic remediation action can be generatedby the remediation component 111 of the carrier server 104 based on thedetermination that the post-delivery diagnostic information in thedistributed electronic ledger 122 is different than the pre-tenderdiagnostic information distributed electronic ledger 122, or based onthe determination that the post-delivery diagnostic informationcorresponds to one or more predefined diagnostic baseline criteria.

In some embodiments, the electronic remediation action that is generatedis an action that is specific to the determination that thepost-delivery diagnostic information included in the detected subsequenttransaction is different than the pre-tender diagnostic informationincluded in the stored transaction. In an embodiment, the electronicremediation action can be automatically generated by the remediationcomponent 111 based further on another determination that thepost-delivery diagnostic information corresponds to one or morepredefined diagnostic baseline criteria. The determination that thepost-delivery diagnostic information corresponds to one or morepredefined diagnostic baseline criteria can be included, for example, inthe notification received from the non-carrier server 112, in someembodiments. In embodiments, the determination that the post-deliverydiagnostic information corresponds to one or more predefined diagnosticbaseline criteria is based on the post-delivery diagnostic information,the notification received from the non-carrier server 112, and/orinformation located in the distributed electronic ledger 122, thatindicates that the end-user computing device 118 is not operating withinpredetermined diagnostic thresholds and/or baselines (e.g. “normal”operations) after delivery.

In further embodiments, the electronic remediation action includesgenerating a return shipping label for the end-user computing device 118for communication to one or more of the non-carrier server or acomputing device of a recipient of the end-user computing device 118.For example, in an embodiment wherein the notification received from thenon-carrier server includes contact information, the electronicremediation action can include using the contact information to generatea return shipping label for the end-user computing device 118. As shownin instance 430 of FIG. 4 , the generated shipping label can becommunicated to the non-carrier server 112. Thereafter, the non-carrierserver 112 can communicate the generated shipping label to theappropriate party, such as the end-user, for return of the end-usercomputing device 118. The shipping label can comprise a data file havingmachine-readable and/or human-readable shipping information that isprintable and can be affixed, as printed, to a package.

Additionally or alternatively, the electronic remediation action canincludes generating a product warranty claim for the end-user computingdevice 118. For example, in an embodiment wherein the notificationreceived from the non-carrier server includes product warrantyinformation, the electronic remediation action can include using theproduct warranty information to generate a product warranty claim forthe end-user computing device 118.

In some embodiments, the transaction component 108 of the carrier server104 can generate a further transaction, subsequent to receipt of thenotification. The further transaction can comprise the generatedelectronic remediation action, embodiments. In such an embodiment, thecommunication component 106 can communicate the generated furthertransaction to the network 102 for storage to the distributed electronicledger 122, as facilitated by the one or more nodes 120.

In further embodiments, instance 420 through instance 430 of FIG. 4 canbe repeated each time that post-delivery diagnostic information isgenerated after delivery, at any time after delivery, and for any numberof occurrences system. As mentioned, in some embodiments, thepost-delivery diagnostic information can indicate system performance asmeasured by a diagnostic test that can be performed at any time afterdelivery. Additionally, post-delivery diagnostic information can begenerated more than once and the post-delivery diagnostic informationcan be communicated, each time, for comparison with the pre-tenderdiagnostic information and/or with a previously-recorded post-deliverydiagnostic information stored in the distributed electronic ledger asone or more transactions. For example, updated post-delivery diagnosticinformation can be generated periodically when the system performance ofthe end-user computing device 118 is periodically tested. Each time adiagnostic system check or test is performed on the end-user computingdevice 118, the results can be communicated to the distributedelectronic ledger as a transaction, the transaction including theupdated post-delivery diagnostic information. The updated post-deliverydiagnostic information can then be compared with the pre-tenderdiagnostic information and/or with previously recorded post-deliverydiagnostic information stored in the distributed electronic ledger.

In such embodiments, the system performance of the end-user computingdevice 118 can be diagnostically tested on command and/or diagnosticallytested automatically via pre-scheduled time markers programmed into theend-user computing device 118. In some embodiments, updatedpost-delivery diagnostic information can be generated more than onceand/or periodically within a predefined period of time, where the periodof time corresponds to a parts warranty and/or a manufacturing warrantythat corresponds to the end-user computing device 118 and/or a serviceplan for the end-user computing device 118. Each time the updatedpost-delivery diagnostic information is generated, it can becommunicated and compared, as previously discussed with regard toinstance 420 through instance 430 of FIG. 4 . The updated post-deliverydiagnostic information can be generated more than once and/orperiodically within a predefined period of time, in some embodiments,where the period of time corresponds to a return policy for the end-usercomputing device 118.

In such embodiments as discussed above, updated post-delivery diagnosticinformation can be generated and communicated for comparison with thepre-tender diagnostic information and/or with previously recordedpost-delivery diagnostic information stored in the distributedelectronic ledger 122, for example, once a week, twice per week,bi-monthly, monthly, quarterly, semi-annually, annually, and/or anotherpredefined period of time. Therefore, post-delivery diagnosticinformation can be communicated to the distributed electronic ledger 122on a reoccurring basis, for example, until the expiration of a warrantyor the expiration of a predefined time period. In an embodiment, thepost-delivery diagnostic information and/or updated post-deliverydiagnostic information is added as one or more transactions to thedistributed electronic ledger 122. In embodiments, updated post-deliverydiagnostic information can be generated from diagnostic testing andcompared with the pre-tender diagnostic information and/or with otherpreviously recorded post-delivery diagnostic information stored in thedistributed electronic ledger 122. Accordingly, in various embodiments,the non-carrier server 112 or the diagnostic assessment component 114thereof use the pre-tender diagnostic information for the end-usercomputing device 118 and post-delivery diagnostic information, garneredat any time after delivery for the end-user computing device 118, todetermine whether the end-user computing device 118 is operational,non-operational, and/or operating within predetermined diagnosticthresholds and/or baselines (e.g. “normal” operations), one or more ofthe previously-described electronic remediation actions can be initiatedand/or performed. Even after the end-user computing device 118 isphysically transferred to a second end-user (e.g., by gift or sale),instances 420 through instance 430 of FIG. 4 can be repeated one or moretimes, to generated updated post-delivery diagnostic information, forexample. Accordingly, warranties can travel or transfer with theend-user computing device 118 for the duration of those warranties, inone example. In further embodiments, the transfer of the user computingdevice 118 is communication as a transaction that is stored in thedistributed electronic ledger 122, for example, for recording transferof a warranty associated with the end-user computing device 118.Additionally or alternatively, one or more notices of a warrantyexpiration can be stored to the distributed electronic ledger 122, assent from the end-user computing device 122 and/or the non-carrierserver 112, for example.

Regarding FIGS. 1 through 4 , it will be understood by those of ordinaryskill in the art that the computing environment 100 and components arenot intended to limit the scope of use or functionality of the presentinvention. Similarly, the computing environment 100 and componentsshould not be interpreted as imputing any dependency and/or anyrequirements with regard to each component and combination(s) ofcomponents illustrated therein. It will be appreciated by those havingordinary skill in the art that the connections illustrated in FIG. 1 arecontemplated to potentially include methods, hardware, software, and/orother devices for establishing a communications link between thecomponents, devices, systems, and/or entities, as can be utilized inimplementation of the present invention. Although the connections aredepicted using one or more solid lines in FIGS. 1 through 4 , it will beunderstood by those having ordinary skill in the art that theconnections can be hardwired or wireless, and can use intermediarycomponents that have been omitted or are not included in the FIGS. 1through 4 for simplicity. As such, the absence of components from FIGS.1 through 4 should be not be interpreted as limiting the presentinvention to exclude additional component(s) and/or combination(s) ofcomponents. Moreover, though devices and components in FIGS. 1 through 4are represented as singular devices and/or components, it will beappreciated that some embodiments can include a plurality of devicesand/or components such that FIGS. 1 through 4 should not be consideredas limiting the number of a devices and/or components.

Turning now to FIGS. 5 and 6 , methods are discussed that can beperformed via one or more of the components and component interactionspreviously described in FIGS. 1 through 4 . As such, the methods arediscussed briefly for brevity, though it will be understood that theprevious discussion and details described therein can be applicable toaspect of the methods of FIGS. 5 and 6 . Additionally or alternatively,it will be understood that the methods discussed herein can beimplemented or performed via the execution of computer-readableinstructions stored on computer readable media, by one or moreprocessors.

FIG. 5 illustrates a method 500 in accordance with an embodiment of thepresent invention. The method 500 can be performed via a computingdevice, in embodiments. The computing device can include a communicationcomponent, such as communication component 106 of FIG. 2 , which canreceive shipment creation information for an item from an entity server.At block 502, the communication component can receive shipment creationinformation for an item from a non-carrier server, wherein the shipmentcreation information includes an item identifier for the end-usercomputing device 118 and pre-tender diagnostic information for theend-user computing device 118. The computing device can include atransaction component, such as transaction component 108 of FIG. 2 ,which can generate a transaction including the shipment creationinformation based on the receipt thereof. At block 504, the transactioncomponent can generate a transaction including the shipment creationinformation based on the receipt thereof. The communication componentcan then communicate the generated transaction to a network, wherein aplurality of nodes of the network is configured to store thecommunicated transaction to a distributed ledger, as illustrated inblock 506.

In some embodiments, the computing device can also include asurveillance component, such as surveillance component 110 of FIG. 2 ,which can monitor the distributed ledger. At block 508, the surveillancecomponent can indirectly (e.g., via one or more nodes) or directlymonitor the distributed ledger, using the network, to detect when asubsequent transaction corresponding to the item identifier is stored inthe distributed ledger, wherein the subsequent transaction includespost-delivery diagnostic information for the end-user computing device118. Additionally or alternatively, the non-carrier server, such asnon-carrier server 112 of FIG. 3 , can indirectly (e.g., via one or morenodes) or directly monitor the distributed ledger, using the network, todetect when a subsequent transaction corresponding to the itemidentifier is stored in the distributed ledger, wherein the subsequenttransaction includes post-delivery diagnostic information for theend-user computing device 118. Continuing, the communication componentcan receive a notification from the non-carrier server, the notificationindicating a determination that the post-delivery diagnostic informationfor the end-user computing device 118 is different than the pre-tenderdiagnostic information for the end-user computing device 118, asdepicted at block 510. In some embodiments, the computing device canfurther include a remediation component, such as remediation component111 of FIG. 2 , which can generate an electronic remediation action. Atblock 512, the remediation component generates an electronic remediationaction based on the determination that the post-delivery diagnosticinformation included in the detected subsequent transaction is differentthan the pre-tender diagnostic information included in the storedtransaction.

FIG. 6 illustrates a method 600 in accordance with an embodiment of thepresent invention. The method 600 can be performed via a computingdevice, in some embodiments. The computing device can include adiagnostic assessment component, such as diagnostic assessment component114 of FIG. 3 , which can receive communications and make diagnosticdeterminations. At block 602, the diagnostic assessment component canreceive a diagnostic assessment for reporting on system performance ofan item prior to tender of the end-user computing device 118 to acarrier entity for shipment. In some embodiments, the diagnosticassessment component can generate pre-tender diagnostic information forthe end-user computing device 118 based on the received diagnosticassessment.

At block 604, the diagnostic assessment component can generate shippingcreation information for communications to a carrier server, wherein theshipment creation information can include the pre-tender diagnosticinformation for the end-user computing device 118 and an item identifierfor the end-user computing device 118. The computing device cansubsequently receive post-delivery diagnostic information for theend-user computing device 118 corresponding to the item identifier, asillustrated at block 606. At block 608, the diagnostic assessmentcomponent can determine whether the post-delivery diagnostic informationmatches the pre-tender diagnostic information stored to the distributedelectronic ledger. In further embodiments, the computing device canretrieve the shipping creation information, stored locally or remotely,for the purposes of the determination.

The computing device can also include a notification component, such asnotification component 116 of FIG. 3 , which can generate notifications.At block 610, when the diagnostic assessment component determines thatthe post-delivery diagnostic information does not match the pre-tenderdiagnostic information, the notification component generates anotification indicating the determination that the post-deliverydiagnostic information does not match the pre-tender diagnosticinformation, the notification including contact information associatedwith the end-user computing device 118. In further embodiments, thecomputing device can retrieve the contact information, stored locally orremotely, for the purposes of generating the notification of saiddetermination. In further embodiments, the notification further includesa request for a remediation action. At block 612, the computing devicecan communicate the generated notification to a carrier server, via anetwork. The carrier server can initiate one or more remediation actionsin response to receipt of the generated notification and/or based on thedeterminations indicated by the notification. In some embodiments, thecomputing device receives a shipping label generated by the carrierserver, wherein the shipping label corresponds to the item identifier ofthe end-user computing device 118 and the shipping label corresponds tothe contact information included in the notification generated by thenotification component.

It is noted that embodiments of the present invention described hereinwith reference to block diagrams and flowchart illustrations, such asthose illustrated in FIGS. 4, 5 and 6 . However, it should be understoodthat each block of the block diagrams and/or flowchart illustrations canbe implemented in the form of a computer program product, an entirelyhardware embodiment, a combination of hardware and computer programproducts, and/or apparatus, systems, computing devices/entities,computing entities, and/or the like carrying out instructions,operations, steps, and similar words used interchangeably (e.g., theexecutable instructions, instructions for execution, program code,and/or the like) on a computer-readable storage medium for execution.For example, retrieval, loading, and execution of code can be performedsequentially such that one instruction is retrieved, loaded, andexecuted at a time. In some embodiments, retrieval, loading, and/orexecution can be performed in parallel such that multiple instructionsare retrieved, loaded, and/or executed together. Thus, such embodimentscan produce specifically-configured machines performing the steps oroperations specified in the block diagrams and flowchart illustrations.Accordingly, the block diagrams and flowchart illustrations supportvarious combinations of embodiments for performing the specifiedinstructions, operations, or steps.

Additionally, as should be appreciated, various embodiments of thepresent disclosure described herein can also be implemented as methods,apparatus, systems, computing devices/entities, computing entities,and/or the like. As such, embodiments of the present disclosure can takethe form of an apparatus, system, computing device, computing entity,and/or the like executing instructions stored on a computer-readablestorage medium to perform certain steps or operations. However,embodiments of the present disclosure can also take the form of anentirely hardware embodiment performing certain steps or operations.

Turning to FIG. 7 , it depicts a block diagram of a computing device 700suitable to implement embodiments of the present invention. It will beunderstood by those of ordinary skill in the art that the computingdevice 700 is just one non-limiting example of a suitable computingdevice and is not intended to limit the scope of use or functionality ofthe present invention. Similarly, the computing device 700 should not beinterpreted as imputing any dependency and/or any requirements withregard to each component and combination(s) of components illustrated inFIG. 7 . It will be appreciated by those having ordinary skill in theart that the connections illustrated in FIG. 7 may comprise othermethods, hardware, software, and/or devices for establishing acommunications link between the components, devices, systems, andentities. Although the connections are depicted using one or more solidlines, it will be understood by those having ordinary skill in the artthat the connections of FIG. 7 can be hardwired or wireless, and can useintermediary components that have been omitted or not included in FIG. 7for simplicity's sake. As such, the absence of components from FIG. 7should be not be interpreted as limiting the present invention toexclude additional components and combination(s) of components.Moreover, though devices and components are represented in FIG. 7 assingular devices and components, it will be appreciated that someembodiments can include a plurality of the devices and components suchthat FIG. 7 should not be considered as limiting the number of a devicesor components.

Continuing, the computing device 700 can be in the form of a server, insome embodiments. Although illustrated as one component in FIG. 7 , thepresent invention can utilize a plurality of local servers and/or remoteservers in the computing device 700. The server can include componentssuch as a processing unit, internal system memory, and a suitable systembus for coupling to various components, including a database or databasecluster. The system bus can be any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, and alocal bus, using any of a variety of bus architectures. By way ofexample, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronic Standards Association (VESA)local bus, and Peripheral Component Interconnect (PCI) bus, also knownas Mezzanine bus.

The server can include or can have access to computer-readable media.Computer-readable media can be any available media that can be accessedby server. Computer-readable media can include one or more of volatilemedia, nonvolatile media, removable media, or non-removable media. Byway of a non-limiting example, computer-readable media can includecomputer storage media and/or communication media. Non-limiting examplesof computer storage media can include one or more of volatile media,nonvolatile media, removable media, or non-removable media, can beimplemented in any method and/or any technology for storage ofinformation, such as computer-readable instructions, data structures,program modules, or other data. In this regard, non-limiting examples ofcomputer storage media can include Random Access Memory (RAM), Read-OnlyMemory (ROM), Electrically Erasable Programmable Read-Only Memory(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disks (DVDs) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage, or other magneticstorage device, or any other medium which can be used to storeinformation and which can be accessed by the server. Generally, computerstorage media is non-transitory such that it does not comprise a signalper se.

Communication media can embody computer-readable instructions, datastructures, program modules, and/or other data in a modulated datasignal, such as a carrier wave or other transport mechanism.Communication media can include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. Non-limiting examples of communication mediacan include wired media, such as a wired network connection, adirect-wired connection, and/or a wireless media, such as acoustic,radio frequency (RF), infrared, and other wireless media. Combinationsof any of the above also can be included within the scope ofcomputer-readable media.

Continuing with FIG. 7 , the a block diagram of a computing device 700suitable for providing packing instructions is provided, in accordancewith an embodiment of the technology. It should be noted that althoughsome components depicted in FIG. 7 are shown in the singular, they canbe plural, and the components can be connected in a different, includingdistributed, configuration. For example, computing device 700 caninclude multiple processors and/or multiple radios. As shown in FIG. 7 ,computing device 700 includes a bus 704 that can directly or indirectlyconnect different components together, including memory 706 and aprocessor 708. In further embodiments, the computing device 700 caninclude one or more of an input/output (I/O) port 710, I/O component712, presentation component 714, or wireless communication component716, such as a radio transceiver. The computing device 700 can becoupled to a power supply 718, in some embodiments.

Memory 706 can take the form of the memory components described herein.Thus, further elaboration will not be provided here, but it should benoted that memory 706 can include any type of tangible medium that iscapable of storing information, such as a database. A database caninclude any collection of records, data, and/or other information. Inone embodiment, memory 706 can include a set of computer-executableinstructions that, when executed, facilitate various functions or stepsdisclosed herein. These instructions will variously be referred to as“instructions” or an “application” for short. Processor 708 can actuallybe multiple processors that can receive instructions and process themaccordingly. Presentation component 714 can include a display, aspeaker, a screen, a portable digital device, and/or other componentsthat can present information through visual (e.g., a display, a screen,a lamp, a light-emitting diode (LED), a graphical user interface (GUI),and/or even a lighted keyboard), auditory (e.g., a speaker), hapticfeedback, and/or other tactile cues. Wireless communication component716 can facilitate communication with a network as previously describedherein. Additionally or alternatively, the wireless communicationcomponent 716 can facilitate other types of wireless communications,such as Wi-Fi, WiMAX, LTE, Bluetooth, and/or other VoIP communications.In various embodiments, the wireless communication component 716 can beconfigured to concurrently support multiple technologies.

I/O port 710 can take a variety of forms. Exemplary I/O ports caninclude a USB jack, a stereo jack, an infrared port, a firewire port,and/or other proprietary communications ports. I/O component 712 cancomprise one or more keyboards, microphones, speakers, touchscreens,and/or any other item useable to directly or indirectly input data intothe computing device 700. Power supply 718 can include batteries, fuelcells, and/or any other component that can act as a power source tosupply power to computing device 700 or to other components.

Although internal components of the computing device 700 are notillustrated for simplicity, those of ordinary skill in the art willappreciate that internal components and their interconnection arepresent in the computing device 700 of FIG. 7 . Accordingly, additionaldetails concerning the internal construction of the computing device 700are not further disclosed herein.

Any and all of the embodiments discussed hereinabove may further be usedalone or in combination with those embodiments discussed in U.S. Pat.No. 10,182,305 B2, filed on Nov. 16, 2015 and having issued on Jan. 15,2019, which is incorporated by reference herein in its entirety.

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in adescriptive sense only and not for purposes of limitation, unlessdescribed otherwise.

What is claimed is:
 1. One or more non-transitory computer-readablemedia having computer instructions stored thereon for execution by oneor more processors, wherein execution of the computer instructions viathe one or more processors results in a method, the method comprising:receiving shipment creation information for an end-user computing devicefrom an entity server, wherein the shipment creation informationincludes an item identifier for the end-user computing device andpre-tender diagnostic information for the end-user computing device,wherein the pre-tender diagnostic information includes one or moreindicators that the end-user computing device is operating within one ormore predetermined thresholds for software and hardware functionalities;generating a transaction including the shipment creation informationbased on the receipt thereof; communicating the generated transaction toa network, wherein a plurality of nodes of the network is configured tostore the communicated transaction to a blockchain; monitoring theblockchain, via the network, to detect when a subsequent transactioncorresponding to the item identifier is stored in the blockchain,wherein the subsequent transaction includes post-delivery diagnosticinformation for the end-user computing device, and the post-deliverydiagnostic information includes one or more indicators that the end-usercomputing device is not operating within at least one of the one or morepredetermined thresholds for the software and hardware functionalities,as determined by a diagnostic application program installed on theend-user computing device; receiving a notification from the entityserver, the notification indicating a determination that thepost-delivery diagnostic information for the end-user computing deviceis different than the pre-tender diagnostic information for the end-usercomputing device, wherein the post-delivery diagnostic information isautomatically captured by the diagnostic application program installedon the end-user computing device and quantifies the software andhardware functionalities of the end-user computing device; andautomatically generating an electronic remediation action in response tothe notification indicating the determination that the post-deliverydiagnostic information included in the detected subsequent transactionis different than the pre-tender diagnostic information included in thestored transaction.
 2. The method of claim 1, further comprising:generating a further transaction, the further transaction comprising thegenerated electronic remediation action; and communicating the generatedfurther transaction to the network for storage to the blockchain by theplurality of nodes.
 3. The method of claim 1, wherein the storedsubsequent transaction further includes the item identifier and thepost-delivery diagnostic information.
 4. The method of claim 1, furthercomprising: identifying, via the network, the stored transaction on theblockchain based on the detection of the subsequent transaction.
 5. Themethod of claim 1, wherein the electronic remediation action isgenerated based further on another determination that the post-deliverydiagnostic information corresponds to one or more predefined diagnosticbaseline criteria.
 6. The method of claim 1, wherein the electronicremediation action is generated based on the notification indicating thedetermination that the post-delivery diagnostic information for theend-user computing device is different than the pre-tender diagnosticinformation for the end-user computing device.
 7. The method of claim 1,wherein the pre-tender diagnostic information reports on systemperformance by quantifying the software and hardware functionalities ofthe end-user computing device.
 8. The method of claim 1, wherein theelectronic remediation action is one or more of generating a returnshipping label for the end-user computing device for communication toone or more of the entity server or a computing device of a recipient ofthe end-user computing device, or generating a product warranty claimfor the end-user computing device.
 9. The method of claim 1, wherein thenotification received from the entity server includes contactinformation, and wherein the electronic remediation action includesusing the contact information to generate a return shipping label forthe end-user computing device.
 10. One or more non-transitorycomputer-readable media having computer instructions stored thereon forexecution by one or more processors, wherein execution of the computerinstructions via the one or more processors results in a method, themethod comprising: receiving shipment creation information for anend-user computing device from an entity server, wherein the shipmentcreation information includes an item identifier for the end-usercomputing device and pre-tender diagnostic information for the end-usercomputing device, wherein the pre-tender diagnostic information includesone or more indicators that the end-user computing device is operatingwithin one or more predetermined thresholds for software and hardwarefunctionalities; generating a transaction including the shipmentcreation information based on the receipt thereof; communicating thegenerated transaction to a network, wherein a plurality of nodes of thenetwork is configured to store the communicated transaction thatincludes the pre-tender diagnostic information as a new block in ablockchain; monitoring the blockchain, via the network, to detect when asubsequent transaction corresponding to the item identifier is stored asanother new block in the blockchain, wherein the other new block for thesubsequent transaction stores post-delivery diagnostic information forthe end-user computing device, and the post-delivery diagnosticinformation includes one or more indicators that the end-user computingdevice is operating within the one or more predetermined thresholds forthe software and hardware functionalities, as determined by a diagnosticapplication program installed on the end-user computing device;receiving a notification from the entity server, the notificationindicating a determination that the post-delivery diagnostic informationfor the end-user computing device stored in the other new block matchesthe pre-tender diagnostic information stored in the new block for theend-user computing device, wherein the post-delivery diagnosticinformation is automatically captured by the diagnostic applicationprogram installed on the end-user computing device and quantifies thesoftware and hardware functionalities of the end-user computing device;and automatically determining that an electronic remediation action isnot to be generated in response to the notification received indicatingthe determination that the post-delivery diagnostic information for theend-user computing device matches the pre-tender diagnostic informationfor the end-user computing device.
 11. A system comprising: one or moreprocessors for: receiving shipment creation information for an end-usercomputing device from an entity server, wherein the shipment creationinformation includes an item identifier for the end-user computingdevice and pre-tender diagnostic information for the end-user computingdevice, wherein the pre-tender diagnostic information includes one ormore indicators that the end-user computing device is operating withinone or more predetermined thresholds for software and hardwarefunctionalities; communicating a generated transaction to a distributednetwork, wherein a plurality of nodes of the distributed network isconfigured to store the communicated transaction to a blockchain;receiving a notification from the entity server, the notificationindicating a determination post-delivery diagnostic information for theend-user computing device is different than the pre-tender diagnosticinformation for the end-user computing device, wherein the post-deliverydiagnostic information is automatically captured by a diagnosticapplication program installed on the end-user computing device andquantifies the software and hardware functionalities of the end-usercomputing device; generating the transaction including the shipmentcreation information based on the receipt thereof of the notificationfrom the entity server of the determination; monitoring the blockchain,via the distributed network, to detect when a subsequent transactioncorresponding to the item identifier is stored in the blockchain,wherein the subsequent transaction includes post-delivery diagnosticinformation for the end-user computing device, and the post-deliverydiagnostic information includes one or more indicators that the end-usercomputing device is not operating within at least one of the one or morepredetermined thresholds for the software and hardware functionalities,as determined by the diagnostic application program installed on theend-user computing device; and automatically generating an electronicremediation action in response to the subsequent transaction thatincludes the determination that the post-delivery diagnostic informationis different than the pre-tender diagnostic information included in thestored transaction.
 12. The system of claim 11, wherein the one or moreprocessors are further configured for generating a further transaction,the further transaction comprising the generated electronic remediationaction and communicating the generated further transaction to thedistributed network for storage to the blockchain.
 13. The system ofclaim 11, wherein the stored subsequent transaction further includes theitem identifier and the post-delivery diagnostic information.
 14. Thesystem of claim 11, wherein the one or more processors are furtherconfigured for identifying, via the distributed network, the storedtransaction on the blockchain based on the detection of the subsequenttransaction.
 15. The system of claim 11, wherein the electronicremediation action is automatically generated based further on anotherdetermination that the post-delivery diagnostic information correspondsto one or more predefined diagnostic baseline criteria.
 16. The systemof claim 11, wherein the electronic remediation action is automaticallygenerated based on the notification indicating the determination thatthe post-delivery diagnostic information for the end-user computingdevice is different than the pre-tender diagnostic information for theend-user computing device.
 17. The system of claim 11, wherein thepre-tender diagnostic information reports on system performance byquantifying the software and hardware functionalities of the end-usercomputing device.
 18. The system of claim 11, wherein the electronicremediation action is one or more of generating a return shipping labelfor the end-user computing device for communication to one or more ofthe entity server or a computing device of a recipient of the end-usercomputing device or generating a product warranty claim for the end-usercomputing device.
 19. The system of claim 11, wherein the notificationreceived from the entity server includes contact information and whereinthe electronic remediation action includes using the contact informationto generate a return shipping label for the end-user computing device.20. The system of claim 19, wherein the electronic remediation actioncomprises the return shipping label for the end-user computing deviceand wherein the electronic remediation action is communicated to theentity server.